Index
Contents

Soft Ventures' SVInstal Version 2.1

Introduction

Operation

Developer's Company Name

Progam Name

Default Load Directory

Windows Program Group Name

Readme Files

Files to be Installed

Syntax, Subdirectories

and multiple source disks

Bulk Load

Icon description, Icon files (.ico)

Redirect File(s) to Windows

File compression

Options

Network Installations

Runtime Support, .TBK, .OVD

Distribution

Shareware Registration


ordering
Shareware Registration

Soft Ventures retains all rights to SVInstal. SVInstal is being marketed as shareware, NOT free software. The shareware concept is simple: try before you buy. If you like Svinstal and wish to continue using it, you are required to register with Soft Ventures. Upon receipt of your $39.95 registration fee, Soft Ventures will send you the latest copy of Svinstal and a printed user's guide. The registered copy removes the shareware notice from SVInstal. You will also be eligible for telephone support and product update notices. This help file makes reference to the Network version of SVInstal. The Network version is included in the registered version.

Shareware registration	$39.95 US + $2.00 shipping

To Order:

Send cheque, money order, company purchase order or fill out ORDER.WRI and mail

or FAX (403)278-0408.

SVInstal can also be registered via CompuServe.  GO SWREG, program ID =  692

Svinstal is an evolving product, if you find you have a requirement that SVInstal does not handle - Give me call, thats how a lot of enhancements are added.

Soft Ventures

Box 22183, Bankers Hall

Calgary, Alberta Canada

T2P 4J5

(403) 278-1681, FAX (403) 278-0408

CompuServe 71441,734

AOL SOFTV1988


Introduction

The installation of a program is a critical time. The new user's first impression can do a lot to help or hinder how your program is accepted. A poor or amature looking installation program can weaken a use's confidence in your program, a problematic installation may cause your program to not work at all. There are many good installation programs on the market today but when I went to purchase one I found most to be over kill (and over priced) for my application. I developed Svinstal to meet the requirement for a simple inexpensive way to get my program and data files from my distribution disk to the users hard drive and build a windows program group.

The objective is to have a program that you can include on your distribution disk that will read a data file also on the distribution. The program SVINSTAL.EXE reads the data file SVINSTAL.SVI which tells it what to install. You include both SVINSTAL.EXE and SVINSTAL.SVI on your distribution floppy. You run the program INST_BLD.EXE to build the data file. The INST_BLD program will contain the filenames to be copied, the name of the default directory to create, the windows program group name and your company name.

It is very simple to use and requires NO programming on your part.

Version 2.0 incorporates the following changes:

SVI_BLD2

"Disk Space Required" option.

Under the new 'options' button, you can set up SVInstal with the minimum disk requirement for your application. Select 'Options' from the main SVI_BLD2 screen, check the 'check minimum disk space' checkbox and enter a value, in megabytes, into the edit box. When SVInstal starts up it will display this information to the user. SVInstal checks the destination disk for required space before beginning to install.

"Bulk Load"

This button allows you to quickly enter multiple filenames into the "Files to be installed" listbox. Clicking on the "Bulk Load" button brings up a standard file dialog box. Select the filenames you wish to add then click on "OK" to load them.

SVI2

New Look

SVI2 presents itself with the popular '3D' type of windows controls for a more polished look.

Changeable background for dialog box.

As SVInstal starts up, it looks for a file named BKG.BMP which is an 8x8 bitmap. If found, it loads this bitmap as the brush to be used for the dialog background. If it fials to find the bitmap file it uses an internal pattern.

Progress gauges.

There are two bar type progress gauges on the main screen. One shows the copy progress (0-100%) of the current file copy operation. The second shows overall installation progress.

"Disk Space Required"

You can now tell your user how much disk space your application is going to need. (see SVI_BLD2 above) SVI2 checks that the destination disk that the user selects has enough room for your programs.

Network support added

Support for installing network applications has been added in Version 2. The network support basicaly boils down to just selecting one of three '.SVI' files to determine what files to install where. SVI2_NET prompts the user to select from one of the install types here:

stand alone - as before, installs to local hard drive.

network server - reads SVISERVE.SVI to install files to a server device.

network client - reads SVICLIEN.SVI (from the already installed server directory) and installs files specific to the client.

This system assumes you need to install most files on the server and some specific files on the client's local machine.

Overwrite prompt removed

The Overwite prompt checkbox has been removed from the SVI2 main screen. If SVI2 encouters the condition where it will be overwriting existing files with the same names, it puts up a standard overwrite prompt dialog box. The user can select 'YES' to just overwrite the current file, 'YES to ALL' to overwrite all existing files, 'NO' to not overwrite the current file or 'CANCEL' to abort the installation.

Faster

The file de-compress function is now twice as fast as it was in previous versions. ( a test file that took 34 sec before, now installs in 14 sec)

Smaller

Even with all the new features added to SVInstal, the program that you put onto your distribution diskette is smaller than it was before.

Compres2

Flexible

Compres2 now just changes the last character of the file's extension. This allows for multiple files with the same filename and different extensions.

ie: 	ABC.TXT  compressed ->  ABC.TX~

ABC.EXE compressed ->  ABC.EX~

SVInstal will still recognize and decompress the old ~SV extension files also.

Faster

Both compression and de-compression have been speeded up by a factor of TWO, while still retaining excellent compression ratios.

Rob Stevens

Soft Ventures

(403) 278-1681


Operation

The SVInstal system is made up of three files:

1. SVINSTAL.EXE, this is what does the installation onto the user's drive. You ship this file on your distribution disk. You can rename it to INSTALL.EXE or whatever you like.

2. SVINSTAL.SVI, this is a small data file that tell SVINSTAL.EXE what files to put where, what directories to build, etc.

3. INST_BLD, this program is run, by the developer, to create the .SVI dtat file. The balance of this help file is dedicated to the operation of INST_BLD.EXE

The SVINSTAL.SVI data file contains information that will direct SVINSTAL.EXE. The program INST_BLD.EXE is the tool used to create this data file.

Developer's Company Name:

This information will appear in the framed title box at the top of the SVINSTAL screen. You can put a company name or your own name, limited to 40 characters.

Program Name:

This will appear with the company name in the SVINSTAL framed title box.

Default Load Directory:

Enter the name of the directory you wish SVINSTAL to create and load your programs into. DO NOT enter drive or subdirectory information. See section Sub-diectories and multiple source disks for syntax on subdirectory use. You are limited to 8 character directory names by DOS.

Windows Program Group Name:

Enter the name you wish to have SVINSTAL use when creating the Windows Program Group. You can use more than 8 characters here but remember too long a name can clutter your user's screen and be annoying. Upper and lower case are accepted.

Readme File Name:

Once your files have been installed and the windows program group created, SVINSTAL will popup a text window with your readme.txt information. You can use a filename other than README.TXT by changing this field. The text window is fully scrollable so you can have a fairly large readme file if you wish. The text window does not do word wrap so you should take care when creating your readme.txt that it will appear correctly. Use Windows Notepad (or any editor that creates a plain ASCII text file) to make your readme.txt file.

Files to be installed:

There are 2 boxes involved in entering your list of files into INST_BLD. The single-line box is the work area , the multi-line box is the actual file list.

To add a new file name, tab to or click in the single-line box. Enter the file name you want added then click the ADD button. Use a ' \ ' to indicate subdirectories, ie: DATA\filename will put filename in the DATA subdirectory. The source files must be in subdirectories of the same name on the floppy diskette, ie: for the above example; the source should be A:\DATA\filename. See the section Sub-diectories and multiple source disks for details on filename syntax.

To edit a file name, select it then click EDIT to bring it up into the single-line work box. When edits are complete, click ADD to put it back.  The edit box will scroll horizontally. You are limited to 80 characters for each entry. (ie: 2:\test\data\longfile.nam,description text)

Note: If no items in the filename list box are selected, the ADD will add the item currently in the work box to the end of the list. If a filename in the list is selected, the ADD inserts the new filename in front of the selected item. This allows you to position file entries in any order you choose. To move an item to a new position in the list box, select it, press EDIT to move it to the work box, select the new position in the list and ADD the file back in.

To delete a file name, select it and click DELETE.

Bulk Load

SVInstal can install up to 500 files. This is a quicker way to get all those filenames into the listbox.

Build/Save:

This button initiates the process of taking the information from the screen and writing it out to a data file. You can save to any file name you wish but when the final version goes onto your distribution floppy, it MUST be called SVINSTAL.SVI.

Open:

This selection is used to load a previously saved data file.

Clear:

Clears the data fields on screen.

Help:

Calls up this help text.


Developer's Company Name:

This information will appear in the framed title box at the top of the SVINSTAL screen. You can put a company name or your own name, limited to 40 characters.


Program Name:

This will appear with the company name in the SVINSTAL framed title box.


Default Load Directory:

Enter the name of the directory you wish SVINSTAL to create and load your programs into. DO NOT enter drive or subdirectory information. See section Sub-diectories and multiple source disks for syntax on subdirectory use. You are limited to 8 character directory names by DOS.


Windows Program Group Name:

Enter the name you wish to have SVINSTAL use when creating the Windows Program Group. You can use more than 8 characters here but remember too long a name can clutter your user's screen and be annoying. Upper and lower case are acceptable as are spaces.


Readme File Name:

SVInstal now supports a variety of ways to use readme files.

1. (as before) Pop up the readme file at the end of the installation.

- this is done by putting the name of the readme file in the appropriate box on the Inst_bld screen.

2. Install the readme file (with notepad icon) in the destination program group.

- this is done by including "README.TXT" in the list of files to install and leaving the Inst_bld readme box EMPTY.

NOTE: the file MUST be called README.TXT

3. Both, pop up the readme.txt AND install it in the program group.

- this is done as in option 2 above, but also put README.TXT in the Inst_bld readme box.

4. 2 Different readme files. You can have SVInstal pop up one readme file and install (with icon) a different readme file.

- this is done by putting readme file names in both places as in option 3 above. NOTE: the readme file to be installed in the program group MUST be called README.TXT, the pop up readme file can be called anything you like.

Use Windows Notepad (or any editor that creates a plain ASCII text file) to make your readme.txt file.


Files to be installed:

There are 2 boxes involved in entering your list of files into INST_BLD. The single-line box is the work area , the multi-line box is the actual file list.

To add a new file name, tab to or click in the single-line box. Enter the file name you want added then click the ADD button. Use a ' \ ' to indicate subdirectories, ie: DATA\filename will put filename in the DATA subdirectory. The source files must be in subdirectories of the same name on the floppy diskette, ie: for the above example; the source should be A:\DATA\filename. See the section Sub-diectories and multiple source disks for details on filename syntax.

To edit a file name, select it then click EDIT to bring it up into the single-line work box. When edits are complete, click ADD to put it back. The edit box will scroll horizontally. You are limited to 80 characters for each entry. (ie: 2:\test\data\longfile.nam,description text)

Note: If no items in the filename list box are selected, the ADD will add the item currently in the work box to the end of the list. If a filename in the list is selected, the ADD inserts the new filename in front of the selected item. This allows you to position file entries in any order you choose. To move an item to a new position in the list box, select it, press EDIT to move it to the work box, select the new position in the list and ADD the file back in.

To delete a file name, select it and click DELETE.


subdir
Syntax, Sub-directories and multiple source disks

Sub-directories and multi-volume source situations are handled by Svinstal. The syntax used when entering files into the filename list tells Svinstal when to build directories and when to ask for disks. The syntax is : (the [ ] items are optional)

[n:][subdir\][(W)]filename[,icon description[,ico filename]]

See the sections on icon description and ico files for details on those respective topics. See Redirect to Windows for description of the (W) parameter.

Examples showing how to enter filnames into the list:

TEST.EXE

- will install into the root install directory from the first diskette. The root install directory is the directory you name in the 'Directory' field of the INST_BLD screen.

DATA\TEST.DAT

- will install the file test.dat into the \DATA subdirectory under the root install directory.

DATA\SAMPLE\TEST.DAT

- will install test.dat into the 'SAMPLE' subdirectory under the 'DATA' subdirectory. NOTE: The same subdirectory structure must exist on the source disk also.

2:TEST.EXE

- will cause Svinstal to put up a message box asking the user to insert disk 2. It will then install into the root install directory. Subsequent entries with 2: will not request a disk change.

3:DATA\TEST.DAT

- will request a disk change, then install into the 'DATA' subdirectory.

Files in the list should be entered in order of directory creation and grouped by disk. Not grouping by disk will still work but your user will be swapping disks in and out and might get annoyed. The disk designation can be only 2 characters, it is recommended that you use 1,2,3,... or you could use A,B,C,... Of course, if you only require a single source diskette, you need not put disk specifiers on at all.


Distribution

You are allowed to include the program SVINSTAL.EXE, with your software, at no charge. You can rename SVINSTAL.EXE to INSTALL.EXE if you want, but the data file included with your program files MUST be named SVINSTAL.SVI (in order for SVINSTAL.to find and use it).

The program INST_BLD.EXE is NOT to be included on your distribution disks.

Note: the file SVIHELP.HLP is the help file for INST_BLD.EXE and is not required for your customer. The help text for Svinstal is included in SVINSTAL.EXE.


Compress

Soft Ventures Svinstal now allows you to compress your files and save space on your distribution disk. The procedure for using file compression is simple:

-> construct your list of files as described in the Files to be installed section.

-> use the Compress utility to compress any files you wish.

(as compression/de-compression adds to the install time, you would be advised to only compress files if you do not have room for the full sized files on your distribution disk.)

-> when copying your files out to your distribution floppy, use the compressed versions.

SVINSTAL.EXE will see the compressed version and de-compress it to the users destination drive.

Remember: put the normal file name in the INST_BLD list of files, but put the compressed file on your distribution disk. eg: enter MYFILE.EXE into the list of files and put the compressed version MYFILE.EX~ on the distribution floppy.


icon_text
Icon description

When you have SVInstal install an executable program (a ".EXE") it will get the icon from the application program and put it into the program group. By default it uses the name of the .EXE as the description for the icon. That means if I have SVPH.EXE in my list of files to be installed, the icon for my SVPaperHanger program will be installed with the Svph under it.

Sometimes that is fine, but you want a more descriptive name - SVInstal can do it. To specify icon description text, place it after the EXE name, separated by a comma.

For example, put this into the list of files:

SVPH.EXE,SV Paper Hanger

To accommodate those situations where you do not want all ".EXE" files to have icons displayed, SVInstal will not add icons if the file extension is ".exe" (lower case).

To have an icon put up for a non-executable file, you need only specify icon description text.

For example,

 ABC.TXT,Read This - will put the notepad icon up for this txt file because Windows has a default association for .TXT files to the notepad. (it will show a different icon if the destination system has a different editor associated with .TXT files)

 XYZ.HLP, Help Info - will put the help icon up  because Windows has a default association for .HLP files to the help system.


ico_files
Icon (.ico) files

If SVInstal encounters an executable file with .EXE (upper case) as the extension, or any file with icon description text, it will ask the Program Manager to put an icon in the program group. For executable files, the Program Manager extracts the icon from the .EXE file. For non executable files (actually for executable files also), SVInstal allows you to specify an icon file.

Syntax for entering filenames into files-to-be-installed listbox:

filename[,icon description[, icon file]]

Examples:

SVINSTAL.EXE

- will use SVINSTAL as the icon description text, and get the icon from the .exe file.

SVINSTAL.EXE,Super Installer

- will use "Super Installer" as the icon description text,, and get the icon from the .exe file.

SVINSTAL.EXE,Super Installer,super.ico

- will use "Super Installer" as the icon description text,, and get the icon from the file super.ico.

 NOTE: You cannot specify an ico file without specifing icon description text. (ie SVINSTAL.EXE,super.ico won't work)


network
Network Installations

The network version on SVInstal, SVI_NET.EXE allows you to supply your user with 3 different installation scenarios, Standalone, Network Server and Network Client. This section outline the differences between these options and setup considerations. The user is shown a "Pre-Installation" dialog from which he chooses the installation type desired.

Standalone

This is the same as a non-network installation. The data file SVINSTAL.SVI is read to determine what files to install and where to put them. This would be used to install your application onto the user's local hard drive. See the Operation section for details on standard installations.

Network Server

This section is used if your application runs from a network server. It is actually the same as the standalone option except that it reads SVISERVE.SVI to get its instructions. This allows you to install different files to the server than would be installed to the local disk if required. The files installed to the server should include both the server files and the client specific files, if you are intending to have the client do a diskless install from the server.

Typically this option would be run by the network administrator so you might choose a different pop-up readme file than for the standalone or client options. This type of installation defaults to not creating a group box.

Network Client

This option reads SVICLIENT.SVI from the previously installed server directory. The filenames put into the files to be installed listbox for this section should be any client specific files such as configuration, or private data files. Also put the .EXE files that you want icons installed for the user. The client install routine will copy non-.EXE files from the server directory. Any files with .EXE extensions will be added to the user's group box, pointing to the actual file on the server.

Typical Installation Steps

1. The network administrator would run a server installation, thereby putting all the files onto the server device.

2. A client installation would be run by running the installation that is now located on the server.


Options

There are three optional setup parameters under the "Options" button.

Disk Space Required

If you wish to specify a minimum amount of free disk space that your user must have before installation, check the "check for minimum space of" checkbox and enter a value in MB. This will show up on the user's installation screen. SVInstal will check that there is enough space available before beginning to copy files.

Type of File to build

To facilitate the three different .SVI file types, you select which one you want to build here. This causes SVI_BLD2 to create a file with the correct format and file extension. See Network Installations for more information on networking.

AfterFile

You can now specify a program to be run upon completion of the installation. SVInstal will run this program at the end of the installation. This could be used for various purposes:

- data initialization

- setting up Windows associations (see supplied example assoc.c)

- change one or more files to be 'Hidden'

- etc.

The program to be run must have been installed as part of the installation. Soft Ventures supplies an example, in C, that sets a Windows association for '.SVI' files. If you would like Soft Ventures to write a custom AfterFile just call (403) 278-1681 for a quote.


bulk
Bulk Load

To assist those of you who are installing applications with LOTS of files (300 is the current limit), version 2.0 now offers a bulk load facility. This loads multiple filenames into the files to be installed listbox. Clicking on the "Bulk Load" button brings up a standard file dialog box. There is a multiple selection list box of filenames. Select the filenames you want to grab. Click on OK to place the selected filenames into the files to be installed listbox.


redirect
ReDirect File(s) to Windows Directory

You can have SVInstal put most of your files to the default directory, but redirect specific files to the Windows directory.

For example you may wish to install a program that changes a user's screen saver (SVSC.EXE) into a directory called \SV, but have SVInstal send your screen saver files to the Windows directory so Windows will find them.

This is accomplished in Version 2.1 by simply putting "(W)" in front of the filename.

In the files to be installed listbox:

SVSC.EXE,Screen Saver Changer  <- This will install into the directory you specify in SVI_BLD.

(w)SVSample.SCR  <- This file will be installed into the Windows directory.

You can also install to the 'System' sub-directory under Windows.

The syntax is (W)system\filename - no "\" after the "(W)", also your source file will need to be in A:\system\filename

See Syntax, Subdirectories and multiple source disks for full information on syntax.


Runtime
Runtime Support

SVInstal has special built in support for various runtime environments.

.TBK

If SVInstal detects a file with an extension of ".TBK", it will insert the following into the icon properties command line:

...\TBOOK.EXE filename.TBK

As is standard in SVInstal, upper case TBK is detected and acted upon, lower case is not. If you wish to have some .TBK files that are not set up as above, simply ensure their extensions are entered in lower case.

By putting "ABC.TBK,My TBK App,icno.ico" into the File-to-be-Installed listbox, you can have it so that when your user clicks on the icon, Windows will start TBOOK.EXE passing it ABC.TBK as the command line parameter. You will need to include TBOOK.EXE and icon.ico as files to be installed also.

.OVD

If SVInstal detects a file with an extension of ".OVD", it will insert the following into the icon properties command line:

...\VISION.EXE filename.OVD

As is standard in SVInstal, upper case OVD is detected and acted upon, lower case is not. If you wish to have some .ovd files that are not set up as above, simply ensure their extensions are entered in lower case.

By putting "XYZ.OVD,My OV App,icno.ico" into the File-to-be-Installed listbox, you can have it so that when your user clicks on the icon, Windows will start VISION.EXE passing it XYZ.OVD as the command line parameter. You will need to include VISION.EXE and icon.ico as files to be installed also.